Reporting terminal capabilities for supporting short message service

ABSTRACT

A method and apparatus for receiving at least one IP-based registration message from a first UE is disclosed. The at least one IP-based registration message may indicate support for short message reception and may include security association data of the first UE, a MSISDN identifier of the first UE, and an IP address of the first UE. Reception of capability information of the first UE is further disclosed. A database may be configured to store the security association data of the first UE, the MSISDN identifier of the first UE, the IP address of the first UE, and the capability information of the first UE. Transmitting, to a second UE, an indication of whether the second UE is or is not capable of IP based short message communication with the first UE is further disclosed.

CROSS REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.14/015,552, filed on Aug. 30, 2013, which is a continuation of U.S.patent application Ser. No. 13/463,293, filed on May 3, 2012, whichissued as U.S. Pat. No. 8,526,981 on Sep. 3, 2013, which is acontinuation of U.S. patent application Ser. No. 12/973,570, filed onDec. 20, 2010, which issued as U.S. Pat. No. 8,175,626 on May 8, 2012,which is a continuation of U.S. patent application Ser. No. 12/777,927,filed on May 11, 2010, which issued as U.S. Pat. No. 7,899,477 on Mar.1, 2011, which is a continuation of U.S. patent application Ser. No.11/112,503, filed on Apr. 22, 2005, which issued as U.S. Pat. No.7,715,856 on May 11, 2010, which claims the benefit of U.S. ProvisionalApplication No. 60/576,700, filed on Jun. 2, 2004, the contents of whichare all hereby incorporated by reference.

FIELD OF INVENTION

The present invention generally relates to wireless local area networks(WLANs), and more particularly, to a method and apparatus for reportingterminal capabilities to support short message service (SMS) over aWLAN.

BACKGROUND

The current architecture for supporting SMS over Internet Protocol (IP)on a WLAN uses a SMS proxy on behalf of the user equipment (UE) at theIP gateway. The SMS proxy acts as a terminal front end to the SignalingSystem No. 7 (SS7) mobile application part (MAP) (i.e., the existing SMSfor global system for mobile communication (GSM)/general packet radioservice (GPRS)). The control signaling associated with SMS is notcurrently covered by the proxy function.

SUMMARY

The present invention extracts the SMS data message from the SS7/MAPformat and sends the message to an interworking WLAN (I-WLAN) UE usingan IP-based protocol. In the present invention, the SMS proxy functionin the SMS IP gateway performs all of the functions performed by the SMSclient in a GSM/GPRS UE.

A method for delivering a short message service (SMS) message to aninterworking wireless local area network user equipment (UE) begins byregistering the UE with an Internet Protocol short message gateway(IP-SM-GW). A capability report is sent from the UE to the IP-SM-GW, thecapability report including the capabilities of the UE. A SMS message istransmitted from a short message service center (SMSC) to the IP-SM-GW.The capabilities of the UE are evaluated at the IP-SM-GW to determinewhether the UE can receive the SMS message, and the SMS message isdelivered to the UE via the IP-SM-GW if the UE has the capabilities toreceive the SMS message.

A method for sending a SMS message from an interworking wireless localarea network user equipment (UE) begins by registering the UE with anIP-SM-GW. A capability report, including the capabilities of the UE, issent from the UE to the IP-SM-GW, whereby the IP-SM-GW acts as a proxyfor the UE. A SMS message is transmitted from the UE to the IP-SM-GW.The SMS message is sent to a SMSC via the IP-SM-GW.

A system for delivering a SMS message to an interworking wireless localarea network user equipment (UE) includes a SMSC, an IP-SM-GW, and acapability report. The SMSC transmits a SMS message for delivery to theUE. The UE registers with the IP-SM-GW, the IP-SM-GW receiving the SMSmessage transmitted by the SMSC. The capability report, including thecapabilities of the UE, is sent from the UE to the IP-SM-GW. TheIP-SM-GW evaluates the capability report and delivers the SMS message tothe UE if the UE has the capabilities to receive the SMS message.

A system for sending a SMS message from an interworking wireless localarea network user equipment (UE) includes an IP-SM-GW, a capabilityreport, and a SMSC. The UE registers with the IP-SM-GW and sends thecapability report, including the capabilities of the UE, to theIP-SM-GW. The IP-SM-GW acts as a proxy for the UE, and receives a SMSmessage sent by the UE. The IP-SM-GW sends the SMS message to the SMSC.

BRIEF DESCRIPTION OF THE DRAWINGS

A more detailed understanding of the invention may be had from thefollowing description of a preferred embodiment, given by way ofexample, and to be understood in conjunction with the accompanyingdrawings, wherein:

FIG. 1 is a block diagram of a SMS system;

FIG. 2 is a flow diagram of a method for delivering a short message to aWLAN UE;

FIG. 3 is a flow diagram of a method for delivering a short message to aWLAN UE using SIP/IMS;

FIG. 4 is a flow diagram of a method for sending a short message from aWLAN UE; and

FIG. 5 is a flow diagram of a method for sending a short message from aWLAN UE using SIP/IMS.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

Hereafter, a user equipment (UE) includes, but is not limited to, awireless transmit/receive unit (WTRU), a mobile station, a fixed ormobile subscriber unit, a pager, or any other type of device capable ofoperating in a wireless environment. When referred to hereafter, a basestation includes, but is not limited to, a Node B, a site controller, anaccess point, or any other type of interfacing device in a wirelessenvironment. Although the following embodiments are described inconjunction with a UE, the embodiments also apply to a WTRU.

FIG. 1 is a diagram of a SMS system 100. The system 100 includes a shortmessage entity (SME) 102 which can send or receive short messages. TheSME 102 communicates with a short message service center (SMSC) 104 thatis responsible for the relaying and the store-and-forwarding of a shortmessage between the SME 102 and a UE.

A gateway mobile switching center (GMSC)/SMS interworking MSC(SMS-IWMSC) 106 has two functions: a GMSC function and a SMS-IWMSCfunction. The GMSC function receives a short message from the SMSC 104,interrogates a home subscriber server (HSS)/home location register (HLR)108 for routing information, and delivers the short message to thevisited MSC or the serving GPRS support node (SGSN) of the recipient UE.The SMS-IWMSC function receives a short message from a UE and submits itto the appropriate SMSC. While shown as separate entities, the SMSC 104and the GMSC/SMS-IWMSC 106 can be integrated into a single entity.

The HSS/HLR 108 communicates with an authentication, authorization, andaccounting (AAA) server 110 for the WLAN. The AAA server 110 containsinformation relating to which UEs can access the WLAN, what services theUEs are permitted to use, and accounting records for each UE.

In a non-IP based setting, the GMSC/SMS-IWMSC 106 communicates with aMSC 112 and a SGSN 114. The MSC 112 and the SGSN 114 both communicatewith a UE 116. The MSC 112 provides functions such as switching,signaling, paging, and inter-MSC handover. The SGSN 114 performsfunctions such as routing and mobility management.

When routing a SMS message, the GMSC/SMS-IWMSC 106 performs a MAPrequest to the HSS/HLR 108 to determine the address of the MSC 112 orthe SGSN 114 where the SMS message is to be routed for delivery to theUE 116.

In an IP based setting, an IP short message gateway (IP-SM-GW) 118provides protocol interworking between the IP client and the network fordelivering a short message. The IP-SM-GW 118 communicates with theGMSC/SMS-IWMSC 106 using established MAP protocols over SS7, appearingto the GMSC/SMS-IWMSC 106 as a MSC or a SGSN. The IP-SM-GW 118 accessesan IP address database 120 to associate a mobile station integratedservice digital network (ISDN) number (MSISDN) with the IP address of aWLAN UE 122. Although the IP database 120 is shown as a separate entity,it may be located in the HSS/HLR 108, in the AAA server 110, in theIP-SM-GW 118, or any other suitable location.

The IP-SM-GW 118 uses a packet data gateway (PDG) 124 to communicatewith the WLAN UE 122. The IP-SM-GW 118 supports registration andauthentication of the WLAN UE 122 for SMS services, and supportssecurity associations with the WLAN UE 122. The IP-SM-GW 118communicates with the WLAN UE 122 using IP based protocols, maintainingthe format and functionality of the SMS message.

When routing a SMS message, the GMSC/SMS-IWMSC 106 performs a MAPrequest to the HSS/HLR 108 to determine the address of the IP-SM-GW 118.In addition, the HSS/HLR 108 provides an indication that the WLAN UE 122is IP based (e.g., communicates with a IP-SM-GW 118 instead of a MSC 112or a SGSN 114), provides the SS7 MAP address of the IP-SM-GW 118, andcontains the necessary logic to determine that the WLAN UE 122 isconnected via IP and return the address of the IP-SM-GW 118 instead ofan address for a MSC or a SGSN. The AAA server 110 maintains the attachstatus of the WLAN UE 122, as to whether the WLAN UE 122 is IP attached.

Delivering Short Messages to a WLAN UE

A method 200 for delivering short messages to a WLAN UE is shown in FIG.2. A tunnel between the WLAN UE 122 and the home PDG 124 is established(step 202). Following establishment of the tunnel, the UE 122 registerswith the IP-SM-GW 118, establishing any necessary security association,authenticates for support of SMS services, and registers the associationbetween the UE's MSISDN (E.164) and its IP address (step 204).

The UE 122 sends its capabilities (as a capability report) to theIP-SM-GW 118 (step 206). The UE capabilities include, for example,memory size, terminal type, screen size, and whether the UE supportssession initiation protocol (SIP). The IP-SM-GW 118 uses the UE'scapabilities to determine whether to reject delivery of a SMS messageand to ensure that only SMS data and notifications are transmitted overIP to the UE 122.

The SMSC 104 forwards a SMS message to the SMS-GMSC 106 (step 208). TheSMS-GMSC 106 interrogates the HSS/HLR 108 to retrieve routinginformation for the UE 122 (step 210). When a user is registered on aWLAN for delivery of SMS messages, the HSS/HLR 108 returns the addressof the IP-SM-GW 118 (rather than the address of the appropriate MSC orSGSN), whereby the IP-SM-GW 118 acts as a proxy for the UE 122 (step212). The SMS proxy (i.e., the IP-SM-GW 118) is able to reject thedelivery of SMS messages based on the capabilities of the UE 122 (e.g.,memory size, screen size, or terminal type) and the nature of the SMSdata (text, animation, etc.).

The SMS-GMSC 106 delivers the SMS message to the IP-SM-GW 118 usingprotocols as if it was a SMS message delivered to a MSC or SGSN (step214). Optionally, the IP-SM-GW 118 interrogates the database 120 toidentify the IP address and relevant security parameters associated withthe UE 122 (step 216).

SMS messages can be delivered by two methods: notification and directdelivery. When the notification delivery method is used, the IP-SM-GW118 sends a SMS notification request to the UE 122 to inform it that aSMS message is available for delivery (step 218). On receipt of the SMSnotification message, the UE 122 responds to the IP-SM-GW 118 with anotification acknowledgement indicating whether it wishes to receive theSMS message (step 220).

If the direct delivery method is used (steps 218 and 220 are skipped),or if a positive acknowledgement is received from the UE 122 in responseto the SMS notification request, the IP-SM-GW 118 delivers the SMSmessage to the UE 122 using one of several possible protocols, e.g.,wireless application protocol (WAP), short message peer to peer protocol(SMPP), mobile message access protocol (MMAP), extensible markuplanguage (XML), or SIP (e.g., an IP multimedia subsystem (IMS) client)(step 222). If the IP-SM-GW 118 rejects delivery of the SMS message,then steps 216-222 are skipped, and the method 200 continues with step224.

The IP-SM-GW 118 sends a delivery report back to the SMS-GMSC 106 (step224). The delivery report either confirms that the SMS message wasdelivered to the UE 122 or informs the SMS-GMSC 106 that the SMS messagecould not be delivered and a reason for the failure. The SMS-GMSC 106sends a SM delivery report status to the HSS/HLR 108 (step 226). TheSMS-GMSC 106 sends the SM delivery report to the SMSC 104 (step 228).Error handling is preferably performed using the mechanisms defined in3GPP Technical Specification (TS) 23.040 v6.3.0 (2004 March), with theIP-SM-GW 118 acting as a front end for the UE 122, although other errorhandling techniques may be used.

FIG. 3 is a flow diagram of a method 300 for delivering a short messageto a WLAN UE 122 using SIP/IMS. The UE 122 registers with a serving callsession control function (S-CSCF) 302 according to the IMS registrationprocedure (step 310). The registration information is also stored in theHSS/HLR 108. The UE 122 sends a capability report to the IP-SM-GW 118(step 312). The UE capabilities include, for example, memory size,terminal type, screen size, and whether the UE supports sessioninitiation protocol (SIP). The IP-SM-GW 118 uses the UE's capabilitiesto determine whether to reject delivery of a SMS message, by acting as aproxy for the UE 122.

The SMSC 104 forwards a SMS message to the SMS-GMSC 106 (step 314). TheSMS-GMSC 106 interrogates the HSS/HLR 108 to retrieve routinginformation (step 316). When a user is IMS registered, the HSS/HLR 108returns the address of the IP-SM-GW 118 along with the address of theMSC.

The SMS-GMSC 106 delivers the SMS message to the IP-SM-GW 118, in thesame manner that it delivers a SMS message to an MSC or a SGSN, carryingthe MSISDN of the target UE 122 (step 318). The IP-SM-GW 118 uses theTEL-URL of the target UE 122 to populate a SIP Request URI, and thensends the SMS message to the S-CSCF 302 using the SIP MESSAGE method(step 320). The S-CSCF 302 then forwards the SIP MESSAGE (SMS message)to the UE 122 (step 322).

Upon receipt of the SIP MESSAGE (SMS message), the UE 122 responds bysending a 200 OK message to the S-CSCF 302 (step 324). It is noted thatthe 200 OK message is not a delivery report, as a 200 OK message cannotcarry the information contained in a delivery report. The S-CSCF 302sends a 200 OK message to the IP-SM-GW (step 326).

The UE 122 then sends a delivery report to the S-CSCF 302 using the SIPMESSAGE method (step 328). Based on filter information, the S-CSCF 302forwards the SIP MESSAGE (delivery report) to the IP-SM-GW 118 (step330), which extracts the delivery report from the SIP MESSAGE format andsends the delivery report to the SMS-GMSC 106 (step 332).

The SMS-GMSC 106 sends a SM delivery report status message to theHSS/HLR 108 (step 334). The SMS-GMSC 106 forwards the delivery report tothe SMSC 104 (step 336). The IP-SM-GW 118 acknowledges that the deliveryreport was sent to the SMSC 104 by sending a 200 OK message to theS-CSCF 302 (step 338). The S-CSCF acknowledges the delivery report tothe UE 122 by sending a 200 OK message to the UE (step 340).

Sending Short Messages from a WLAN UE

FIG. 4 is a diagram of a method 400 for sending a short message from theWLAN UE 122. A tunnel between the UE 122 and the home PDG 124 isestablished (step 402). Following establishment of the tunnel, the UE122 registers with the IP-SM-GW 118 establishing any necessary securityassociation, authenticates for support of SMS services, and registersthe association between the UE's MSISDN (E.164) and its IP address (step404). The association information for the UE 122 is also recorded in theHSS/HLR 108. The UE 122 sends its capability information to the IP-SM-GW118 to enable the SMS terminal proxy operation (step 406). After sendingthe capability information, the IP-SM-GW 118 handles all SMS controlmessages for the UE 122 (step 408).

The UE 122 delivers a SMS message to the IP-SM-GW 118, using e.g., WAP,SMPP, MMPP, or XML (step 410). The IP-SM-GW 118 extracts the SMS messageand forwards it to the SMS-IWMSC 108 using the standard MAP, as if theIP-SM-GW 118 was a MSC or a SGSN (step 412).

The SMS-IWMSC 106 forwards the SMS message to the SMSC 104 (step 414).Upon receipt of the SMS message, the SMSC 104 sends a delivery report tothe SMS-IWMSC 106 (step 416). The SMS-IWMSC 106 sends the deliveryreport to the IP-SM-GW 118 (step 418). The delivery report is sent withan indication of whether the delivery was a success or a failure. Ifthere was a delivery failure, the SMSC 104 reports back to the SMS-IWMSC106 and the SMS-IWMSC 106 will attempt to retransmit the SMS message. Ifthe number of retries exceeds a threshold, then a delivery failurereport will be sent to the UE 122.

The IP-SM-GW 118 sends the delivery report to the UE 122 using aproprietary mechanism and/or protocols (step 420). In a preferredembodiment, the delivery report is sent via an IP-based transfer, suchas SMPP. The delivery report either confirms that the SMS message wasdelivered to the SMSC 104 or informs the UE 122 that the SMS messagecould not be delivered and a reason for the failure.

As with message receipt, the error handling for message sending ispreferably performed using the mechanisms defined in TS 23.040 v6.3.0(2004 March), with the IP-SM-GW 118 acting as a front end for the UE122, although other error handling techniques may be used.

The implementation of new procedures in the I-WLAN UE side is reduced,where only simple operations are performed to confirm reception of theSMS data or to report a corrupt message for retransmission purposes.

FIG. 5 is a flow diagram of a method 500 for sending a short messagefrom a WLAN UE 122 using SIP/IMS. The UE 122 registers with a S-CSCF 502according to the IMS registration procedure (step 510). The registrationinformation is also stored in the HSS/HLR 108. The UE 122 sends acapability report to the IP-SM-GW 118 (step 512). The UE capabilitiesinclude, for example, memory size, terminal type, screen size, andwhether the UE supports session initiation protocol (SIP). The IP-SM-GW118 uses the UE's capabilities to enable SMS terminal proxy operation,allowing the IP-SM-GW 118 to handle all SMS control messages for the UE122.

The UE 122 submits a SMS message to the S-CSCF 502 using the SIP MESSAGEmethod (step 514). The S-CSCF 502 forwards the SIP MESSAGE (SMS message)to the IP-SM-GW 118 based on filter information (step 516). The IP-SM-GW118 indicates that the SIP MESSAGE (SMS message) was received by sendinga SIP 202 Accepted message to the S-CSCF 502 (step 518). The messagereceipt information is forwarded by the S-CSCF 502 to the UE 122 by aSIP 202 Accepted message (step 520).

The IP-SM-GW 118 extracts the SMS message from the SIP MESSAGE andforwards it to the SMS-IWMSC 106 using standard MAP signaling (step522). The address of the SMSC 104 is extracted either from the R-URI ofthe SIP MESSAGE or from the SMS content. The SMS-IWMSC 106 forwards theSMS message to the SMSC 104 (step 524).

The SMSC 104 sends a submit report to the SMS-IWMSC 106 (step 526). Thesubmit report is an acknowledgement that the SMS message was received bythe SMSC 104. The SMS-IWMSC 106 sends the submit report to the IP-SM-GW118 (step 528). The IP-SM-GW 118 sends the submit report to the S-CSCF502 using the SIP MESSAGE method (step 530). The S-CSCF 502 forwards theSIP MESSAGE (submit report) to the UE 122 (step 532). The UE 122acknowledges receipt of the SIP MESSAGE (submit report) by sending a 200OK message to the S-CSCF 502 (step 534), which is then forwarded to theIP-SM-GW 118 (step 536).

Although the features and elements of the present invention aredescribed in the preferred embodiments in particular combinations, eachfeature or element can be used alone (without the other features andelements of the preferred embodiments) or in various combinations withor without other features and elements of the present invention.

What is claimed is:
 1. A method for operation in a network device, themethod comprising: receiving at least one Internet Protocol (IP)-basedregistration message from a first user equipment (UE), wherein the atleast one IP-based registration message indicates support for shortmessage reception and includes security association data of the firstUE, a mobile station international subscriber directory number (MSISDN)identifier of the first UE, and an IP address of the first UE; receivingcapability information of the first UE, wherein the capabilityinformation includes a terminal type; storing, in a database, thesecurity association data of the first UE, the MSISDN identifier of thefirst UE, the IP address of the first UE, and the capability informationof the first UE; and receiving, from a second UE, an IP-based messageincluding the MSISDN identifier of the first UE; determining, based onthe capability information of the first UE, whether the second UE iscapable of internet protocol (IP) based short message communication withthe first UE; and transmitting, to the second UE, an indication ofwhether the second UE is or is not capable of internet protocol (IP)based short message communication with the first UE.
 2. The methodaccording to claim 1, wherein the at least one IP-based registrationmessage is received over a wireless local area network (WLAN).
 3. Themethod according to claim 1, wherein the IP-based message including theMSISDN identifier of the first UE is received over a wireless local areanetwork (WLAN).
 4. The method according to claim 1, further comprising:on a condition that the second UE is not capable of internet protocol(IP) based short message communication with the first UE, transmitting areject message to the second UE.
 5. The method according to claim 1,further comprising: transmitting, to the first UE, the stored MSISDNidentifier of the second UE.
 6. The method according to claim 1, whereinthe received at least one IP-based registration message and the receivedcapability information of the first UE are received over an IP tunnel.7. A network device comprising: a receiver configured to receive atleast one Internet Protocol (IP)-based registration message from a firstuser equipment (UE), wherein the at least one IP-based registrationmessage indicates support for short message reception and includessecurity association data of the first UE, a mobile stationinternational subscriber directory number (MSISDN) identifier of thefirst UE, and an IP address of the first UE; the receiver furtherconfigured to receive capability information of the first UE, whereinthe capability information includes a terminal type; a databaseconfigured to store the security association data of the first UE, theMSISDN identifier of the first UE, the IP address of the first UE, andthe capability information of the first UE; and the receiver furtherconfigured to receive, from a second UE, an IP-based message includingthe MSISDN identifier of the first UE; circuitry configured todetermine, based on the capability information of the first UE, whetherthe second UE is capable of internet protocol (IP) based short messagecommunication with the first UE; and a transmitter configured totransmit, to the second UE, an indication of whether the second UE is oris not capable of internet protocol (IP) based short messagecommunication with the first UE.
 8. The network device according toclaim 7, wherein the receiver is further configured to receive at leastone IP-based registration message over a wireless local area network(WLAN).
 9. The network device according to claim 7, wherein the IP-basedmessage including the MSISDN identifier of the first UE is received overa wireless local area network (WLAN).
 10. The network device accordingto claim 7, further comprising: on a condition that the second UE is notcapable of internet protocol (IP) based short message communication withthe first UE, transmitting a reject message to the second UE.
 11. Thenetwork device according to claim 7, further comprising: a transmitterconfigured to transmit to the first UE, the stored MSISDN identifier ofthe second UE.
 12. The network device according to claim 7, wherein thereceived at least one IP-based registration message and the receivedcapability information of the first UE are received over an IP tunnel.13. A method for operation in a first user equipment (UE), the methodcomprising: transmitting, from the first UE to a network node, at leastone Internet Protocol (IP)-based registration message, wherein the atleast one IP-based registration message indicates support for shortmessage reception and includes security association data of the firstUE, a mobile station international subscriber directory number (MSISDN)identifier of the first UE, and an IP address of the first UE;transmitting, from the first UE to the network node, capabilityinformation including a terminal type; and receiving, by the first UEfrom a second UE, an IP-based message including the MSISDN identifier ofthe first UE, wherein the IP-based message is formatted according to thetransmitted capability information.
 14. The method according to claim13, wherein the least one IP-based registration message is transmittedover a wireless local area network (WLAN).
 15. The method according toclaim 13, wherein the IP-based message including the MSISDN of the firstUE is received over a wireless local area network (WLAN).
 16. The methodaccording to claim 13, wherein the transmitted at least one IP-basedregistration message and the transmitted capability information of thefirst UE are transmitted over an IP tunnel.
 17. A first user equipment(UE) comprising: a transmitter configured to transmit, from the first UEto a network node, at least one Internet Protocol (IP)-basedregistration message, wherein the at least one IP-based registrationmessage indicates support for short message reception and includessecurity association data of the first UE, a mobile stationinternational subscriber directory number (MSISDN) identifier of thefirst UE, and an IP address of the first UE; the transmitter furtherconfigured to transmit, from the first UE to the network node,capability information including a terminal type; and a receiverconfigured to receive, from a second UE, an IP-based message includingthe MSISDN identifier of the first UE, wherein the IP-based message isformatted according to the transmitted capability information.
 18. TheUE according to claim 17, wherein the least one IP-based registrationmessage is transmitted over a wireless local area network (WLAN). 19.The UE according to claim 17, wherein the IP-based message including theMSISDN of the first UE is received over a wireless local area network(WLAN).
 20. The UE according to claim 17, wherein the transmitted atleast one IP-based registration message and the transmitted capabilityinformation of the first UE are transmitted over an IP tunnel.